Skip to main content

This is a new service – your feedback will help us to improve it.

Royal Borough of Kensington and Chelsea

Article 4 direction area

There is a problem

  • 84 issue of type invalid category value

Article 4 - No 8

reference
3
name
Article 4 - No 8
article-4-direction
3
permitted-development-rights

undefined

Minor alterations in Conservation Areas
uprns
address-texts
geometry
MULTIPOLYGON (((-0.196250 51.497040,-0.196180 51.497060,-0.196090 51.497080,-0.196110 51.497110,-0.196120 51.497120,-0.196170 51.497220,-0.196180 51.497230,-0.196180 51.497240,-0.196230 51.497280,-0.196310 51.497360,-0.196350 51.497350,-0.196380 51.497350,-0.196420 51.497340,-0.196450 51.497330,-0.196510 51.497320,-0.196420 51.497180,-0.196360 51.497070,-0.196350 51.497060,-0.196330 51.497020,-0.196250 51.497040)),((-0.196580 51.497310,-0.196590 51.497300,-0.196650 51.497290,-0.196660 51.497290,-0.196730 51.497270,-0.196800 51.497260,-0.196830 51.497260,-0.196880 51.497250,-0.196940 51.497230,-0.196930 51.497210,-0.196900 51.497160,-0.196840 51.497170,-0.196820 51.497130,-0.196790 51.497080,-0.196760 51.497040,-0.196730 51.496990,-0.196710 51.496940,-0.196700 51.496940,-0.196540 51.496980,-0.196470 51.496990,-0.196400 51.497010,-0.196420 51.497040,-0.196430 51.497060,-0.196490 51.497160,-0.196490 51.497170,-0.196580 51.497310)))
point
POINT (-0.196507 51.497155)
notes
entry-date
2025-01-03
start-date
end-date

How to fix this issue

Your data is missing a permitted-development-rights.

The Article 4 direction area guidance explains how to fix the issue:

permitted-development-rights

A list of the permitted development rights withdrawn by the article 4 direction.

Separate the rights in the list using semicolons.

Only use rights from our permitted development right dataset. If the area withdraws a permitted development right that is not in our dataset, email digitalland@communities.gov.uk.

Example: 3D;3M;11B

How to improve Royal Borough of Kensington and Chelsea’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL